Performing scheduled backups of a backup node associated with a plurality of agent nodes

ABSTRACT

Provided are a method, system, and program for performing scheduled backups of a backup node associated with a plurality of agent nodes. Backup data sets on at least one machine in a network are associated with a backup node and a plurality of agent nodes in the network are associated with the backup node. The agent nodes are associated with machines in the network capable of backing up the backup data sets associated with the backup node. A schedule indicating a scheduled backup to backup scheduled data sets associated with the backup node is processed. At least one of the agent nodes is contacted to request the at least one agent node to perform the scheduled backup and backup the scheduled data sets, wherein the at least one contacted agent node performs the scheduled backup to backup the scheduled backup sets.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to a method, system, and program forperforming scheduled backups of a backup node associated with aplurality of agent nodes.

2. Description of the Related Art

In a network backup environment, a client system may backup data in astorage device and coordinate the backup with a backup server. Forinstance, the International Business Machines (“IBM”®) Tivoli® StorageManager product provides software for a client and server systems tobackup client data. (IBM and Tivoli are registered trademarks of IBM).

In a backup environment of multiple client nodes, one client node maylogon to the backup server to perform backup operations on behalf ofanother node having data sets to backup, which may be part of ascheduled backup. To schedule a backup operation, a backup operation maybe scheduled for one node to backup data sets in an attached storage atthat node or a set of backup operations may be defined and associatedwith nodes to perform the scheduled backup. In the second technique, aschedule is defined and nodes are associated with that schedule.

SUMMARY

Provided are a method, system, and program for performing scheduledbackups of a backup node associated with a plurality of agent nodes.Backup data sets on at least one machine in a network are associatedwith a backup node and a plurality of agent nodes in the network areassociated with the backup node. The agent nodes are associated withmachines in the network capable of backing up the backup data setsassociated with the backup node. A schedule indicating a scheduledbackup to backup scheduled data sets associated with the backup node isprocessed. At least one of the agent nodes is contacted to request theat least one agent node to perform the scheduled backup and backup thescheduled data sets, wherein the at least one contacted agent nodeperforms the scheduled backup to backup the scheduled backup sets.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an embodiment of a network computing environment.

FIG. 2 illustrates an embodiment of backup node information.

FIG. 3 illustrates an embodiment of a scheduled backup.

FIGS. 4, 5, 6, and 7 illustrate embodiments of operations to backup datasets in a scheduled backup.

DETAILED DESCRIPTION

In the following description, reference is made to the accompanyingdrawings which form a part hereof and which illustrate severalembodiments of the present invention. It is understood that otherembodiments may be utilized and structural and operational changes maybe made without departing from the scope of the present invention.

FIG. 1 illustrates a network computing environment having a plurality ofmachine nodes 2 a and 2 b (two are shown, but there may be more), aplurality of storage devices 4 a, 4 b, 4 c (three are shown, but theremay be more), and a server 6 that communicate over a network 8. Themachine nodes 2 a, 2 b include backup client 10 a, 10 b program and theserver 6 includes a backup server 12 program to coordinate machine node2 a, 2 b operations to backup data sets in the storage devices 4 a, 4 b,4 c to backup storage 14. The. storage devices, e.g., 4 a, may becoupled to machine nodes, 2 b, and connect to the network 8 via theconnected machine node 2 b. The backup server 12 maintains a backupschedule 16 of backup operations to perform, node information 18providing information on the network nodes involved in backupoperations, and logging information 20 that the backup server 12 logsfor backup operations.

To backup data, the machine nodes 2 a, 2 b may backup data from attachedstorage devices to the server 6, which then backups the data sets inbackup storage 14. Alternatively, in a LAN free backup operation, themachine nodes 2 a, 2 b coordinate backup operations with the server 6via a separate network, such as a Local Area Network (LAN), and then themachine nodes 2 a, 2 b directly backup data from the storage devices 4a, 4 b, 4 c over the network 8, which may comprise a Storage AreaNetwork (SAN), to the backup storage 14. The backup storage 14 may beattached directly to the network 8, such as shown in FIG. 1, or becoupled to the server 6 and connect to the network 8 through the server6.

The machine nodes 2 a, 2 b may comprise suitable computational devicesknown in the art, such as servers, desktop computers, workstations,mainframes, hand held computing devices, telephony devices, etc. capableof interfacing with a backup server 6. The storage devices 4 a, 4 b, 4 cmay comprise any suitable storage device known in the art, such as astorage system including a plurality of storage devices, e.g.,interconnected hard disk drives (a Redundant Array of Independent Disks(RAID), Just a Bunch of Disks (JBOD), Direct Access Storage Device(DASD), disks connected in a loop configuration (serial loop, FibreChannel Arbitrated Loop), a tape library, an optical library, a networkattached storage (NAS), etc. Alternatively, the storage devices maycomprise local storage, e.g., 4 a, within or attached to a machine node,e.g., 2 b. The storage devices 4 a, 4 b, 4 c comprise network nodeshaving storage. The storage device nodes 4 a, 4 b, 4 c may include abackup client program (not shown) that allows them to coordinate withthe backup server 12 to transfer their data sets to the backup storage14. The server 6 may comprise a suitable server system known in the artto manage backup messages from multiple systems. The backup storage 14may comprise suitable non-volatile storage systems known in the art,such as tape storage, hard disk drives, optical storage, etc. Thenetwork 8 may comprise one or more networks known in the art, such as aWide Area Network (WAN), Local Area Network (LAN), Storage Area Network(SAN), wireless network, the Internet, and Intranet, etc.

FIG. 2 illustrates an embodiment of the node information 50 for a backupnode, comprising: a backup node identifier (ID) 52; an agent list 54that associates a plurality of agent nodes comprising machine nodes 2 a,2 b in the network 8 with the backup node; and backup data sets 56. Theidentified agent nodes in the agent list 54 are assigned to backup theindicated backup data sets 56. The backup data sets 56 may include datasets in different storage devices 4 a, 4 b, 4 c in the network 8, suchthat the backup data set 56 information identifies a location in thenetwork 8 and a location in the storage device 4 a, 4 b, 4 c of the datato backup. The agent list 54 may further indicate a status of the agentmachine nodes 2 a, 2 b, such as whether they are available toparticipate in a backup of the backup data sets 56 for the node.

In one embodiment, a backup node 50 may comprise a virtual node in thatthere is no physical machine node 2 a, 2 b directly corresponding to thebackup node 50. The machine nodes 2 a, 2 b indicated in the agent list54 comprise the computational resources that correspond to the backupnode 50 and that are designated to backup the backup sets 56 defined forthe backup node 50. Further, the data sets for a virtual backup node maybe distributed across multiple physical storage devices 4 a, 4 b, 4 c. Avirtual backup node 50 may be used to group data sets in distributedstorage 4 a, 4 b, 4 c that have common characteristics, such as a commonbackup policy, common source, common importance, etc. Alternatively, thebackup node 50 may comprise a machine node, e.g., 2 b having attachedstorage, e.g., 4 b, and the agent nodes indicated in the agent list 54comprise additional machine nodes 2 a on the network 8 that are assignedto backup the backup data sets 56 of the backup node 50. In either case,when an agent node performs operations on behalf of the backup node,which may comprise a virtual or physical machine node, the agent nodemay act on behalf of the backup node so that the backup operations theagent node performs on behalf of the backup node are logged by thebackup server 12 as performed by the backup node in the log information20.

FIG. 3 illustrates an embodiment of a scheduled backup 70 that may beincluded in the backup schedule 16 the backup server 12 executes. Ascheduled backup 70 includes a schedule identifier (ID) 72; a backupschedule 74 indicating backup day and/or times to perform the backup ofthe scheduled backup 70; and a backup node 76 to backup. The backup node76 may represent a virtual node associated with multiple machine nodes 2a, 2 b identified in the agent list 54.

FIG. 4 illustrates an embodiment of operations performed by the backupserver 12 executed by the server 6 to process a scheduled backup 70.Upon initiating (at block 100) the processing of one scheduled backup 70to backup the scheduled data sets 56 associated with the backup node 50,the backup server 12 contacts (at block 102) at least one of the agentnodes 2 a, 2 b indicated in the agent list 54 for the backup node 50 torequest the at least one contacted agent node to perform the scheduledbackup of the backup data sets 56 associated with the backup node. If(at block 104) the contacted agent node is capable of performing thescheduled backup 50, then the backup server 12 assigns (at block 106)the scheduled backup to the available contacted agent node. If (at block104) the contacted agent node is not available, then the backup server12 may indicate (at block 108) in the agent list 54 that the contactedagent node is not available to perform the scheduled backup 50. An agentnode indicated in the agent list 54 as not available would not becontacted during a subsequent processing of the scheduled backup 50. Anagent node may be unavailable if there is a device failure of the agentnode or network failure to the agent node or the agent node does nothave sufficient computational resources available to handle all or aportion of the scheduled backup, i.e., it is too busy. The backup server12 may assign all or a portion of the backup data sets 56 to anavailable agent node 2 a, 2 b. For instance, the backup server 12 mayautomatically distribute the backup data sets 56 to multiple availableagent nodes 2 a, 2 b to balance the workload. Alternatively, if theagent nodes 2 a, 2 b are contacted serially, then each agent node may beassigned as many of the backup data sets 56 that the contacted agentnode can process given its current workload.

FIG. 5 illustrates an embodiment of operations performed by the backupserver 12 to serially select agent nodes 2 a, 2 b in the agent list 54to process the scheduled backup operation 70. Upon initiating (at block150) an operation to contact agent nodes to perform the scheduledbackup, which may comprise the operation at block 102 in FIG. 4, thebackup server 12 contacts (at block 152) a first agent node according toa serial ordering of the agent nodes in the agent list 54. If (at block154) the contacted agent node is available to perform the scheduledbackup, then the backup server 12 enables (at block 156) the contactedagent node to perform the scheduled backup. Otherwise, if (at block 154)the contacted agent node is unavailable, i.e., the contacted agent nodeis too busy or there is a network or device failure causing thecontacted agent node to be unavailable, then the backup server 12contacts (at block 158) a next agent node according to the serial orderindicated in the agent list 54. As discussed, the serially contactedagent nodes in the agent list 54 may perform a portion or all of thescheduled backup operation. In an alternative embodiment, nodes may beassigned portions of a file to backup. In such case, after block 156,the backup server 12 may continue to contact nodes to locate nodes toperform portions of the work to distribute the work among multiple nodesand allow for concurrent backup of the data.

FIG. 6 illustrates an embodiment of operations performed by the backupserver 12 to broadcast messages to all agent nodes 2 a, 2 b in the agentlist 54 to process the backup operation. Upon initiating (at block 180)an operation to contact agent nodes to perform the scheduled backup,which may comprise the operation at block 102 in FIG. 4, the backupserver 12 broadcasts (at block 182) a message to all agent nodes 2 a, 2b indicated in the agent list 54 to determine which agent nodes areavailable to backup the scheduled backup data sets 56. If (at block 184)the backup server 12 prefers to use multiple agent nodes in the backup,then the backup server 12 selects (at block 186) multiple agent nodes 2a, 2 b that respond indicating availability to perform the scheduledbackup of the backup node's 74 backup data sets 56. The backup server 12assigns (at block 188) a portion of the scheduled data sets to each ofthe selected agent nodes 2 a, 2 b to perform the scheduled backup withrespect to the assigned portion. The backup server 12 may distribute thescheduled data sets 56 to balance the workload among the available agentnodes. If the backup server 12 prefers to use a single agent node, thenthe backup server 12 selects (at block 190) one agent node responding tothe broadcast message indicating availability to perform the scheduledbackup to perform the scheduled backup of the backup data sets 56.

In the embodiment of FIG. 6, if less than all the agent nodes to whichthe broadcast is directed respond, then those responding and availableagents will be assigned backup data sets to backup. Thus, failure ofsome of the agents to respond is tolerated and those agents that areavailable are then used to handle the scheduled backup. A node may notbe available if node client is down or if node responds indicating thatit is too busy to assist with the scheduled backup.

FIG. 7 illustrates authentication operations performed by the backupserver 12 to log information about backup operations performed by oneagent node 12 on behalf of the backup node 50 subject to the backup,where the backup node may comprise a virtual node. The agent nodes 2 a,2 b upon being selected to perform backup operations would logon to thebackup server 12 to initiate the backup operations on behalf of thebackup node 50 subject to the scheduled backup. The agent node 2 a, 2 bmay act on behalf of the backup node when performing the scheduledbackup. Upon receiving (at block 220) a request to logon by one agentnode performing the scheduled backup using an agent node credential, thebackup server 12 determines (at block 222) whether the agent nodecredential is valid. If not, the backup server 12 denies (at block 224)the logon. Otherwise, if the credential is valid, the backup server 12enables (at block 226) the client to logon and perform operationspursuant to what the valid credential permits. Upon receiving (at block228) a request by the agent node logged on with the agent nodecredential to operate as the backup node, the backup server 12determines (at block 230) whether the requesting agent node isauthorized to act on behalf of the backup node. If not, then the backupserver 12 denies (at block 232) the agent request to act on behalf ofthe backup node. Otherwise, if the authentication succeeds, then thebackup server 12 enables (at block 234) the requesting agent node toperform operations to backup the scheduled data sets acting on behalf ofthe backup node. The backup server 12 logs (at block 236) information 20on backup operations the agent node 2 a, 2 b performs to backup thescheduled data sets as operations of the backup node. Further, thebackup server 12 may indicate (at block 238) in the logging information20 that the agent node is operating as the backup node.

Described embodiments provide techniques to define a backup node in thenetwork, where a plurality of machine nodes in the network may bedesignated as agent nodes to backup the backup sets assigned to thedefined backup node. Any operations an agent node performs on behalf ofthe backup node may be logged as performed by the backup node, such thatthe agent node acts on behalf of the backup node.

Additional Embodiment Details

The described operations may be implemented as a method, apparatus orarticle of manufacture using standard programming and/or engineeringtechniques to produce software, firmware, hardware, or any combinationthereof. The term “article of manufacture” as used herein refers to codeor logic implemented in hardware logic (e.g., an integrated circuitchip, Programmable Gate Array (PGA), Application Specific IntegratedCircuit (ASIC), etc.) or a computer readable medium, such as magneticstorage medium (e.g., hard disk drives, floppy disks, tape, etc.),optical storage (CD-ROMs, optical disks, etc.), volatile andnon-volatile memory devices (e.g., EEPROMs, ROMs, PROMs, RAMs, DRAMs,SRAMs, firmware, programmable logic, etc.). Code in the computerreadable medium is accessed and executed by a processor. The code inwhich preferred embodiments are implemented may further be accessiblethrough a transmission media or from a file server over a network. Insuch cases, the article of manufacture in which the code is implementedmay comprise a transmission media, such as a network transmission line,wireless transmission media, signals propagating through space, radiowaves, infrared signals, etc. Thus, the “article of manufacture” maycomprise the medium in which the code is embodied. Additionally, the“article of manufacture” may comprise a combination of hardware andsoftware components in which the code is embodied, processed, andexecuted. Of course, those skilled in the art will recognize that manymodifications may be made to this configuration without departing fromthe scope of the present invention, and that the article of manufacturemay comprise any information bearing medium known in the art.

The illustrated operations of FIGS.4-7 show certain events occurring ina certain order. In alternative embodiments, certain operations may beperformed in a different order, modified or removed. Moreover, steps maybe added to the above described logic and still conform to the describedembodiments. Further, operations described herein may occur sequentiallyor certain operations may be processed in parallel. Yet further,operations may be performed by a single processing unit or bydistributed processing units.

The foregoing description of various embodiments of the invention hasbeen presented for the purposes of illustration and description. It isnot intended to be exhaustive or to limit the invention to the preciseform disclosed. Many modifications and variations are possible in lightof the above teaching. It is intended that the scope of the invention belimited not by this detailed description, but rather by the claimsappended hereto. The above specification, examples and data provide acomplete description of the manufacture and use of the composition ofthe invention. Since many embodiments of the invention can be madewithout departing from the spirit and scope of the invention, theinvention resides in the claims hereinafter appended.

1. A method, comprising: associating backup data sets on at least onemachine in a network with a backup node; associating a plurality ofagent nodes in the network with the backup node, wherein the agent nodesare associated with machines in the network capable of backing up thebackup data sets associated with the backup node; processing a scheduleindicating a scheduled backup to backup scheduled data sets associatedwith the backup node; and contacting at least one of the agent nodes torequest the at least one agent node to perform the scheduled backup andbackup the scheduled data sets, wherein the at least one contacted agentnode performs the scheduled backup to backup the scheduled backup sets.2. The method of claim 1, wherein the backup node comprises a virtualnode, and wherein at least one backup data set associated with thebackup node is implemented within one node on the network that isdifferent from at least one agent node associated with the backup node.3. The method of claim 1, wherein the scheduled data sets are located onstorage devices in the network, wherein the agent nodes backup thescheduled data sets by communicating with the storage devices over thenetwork to cause a transfer of the scheduled data sets from the storagedevices to backup storage.
 4. The method of claim 1, whereincommunicating with the at least one agent node comprises: contacting atleast one agent node to determine whether the agent node is available toperform the scheduled backup; and assigning the scheduled backup to thecontacted agent node in response to determining that the agent node isavailable to perform the scheduled backup.
 5. The method of claim 4,further comprising: indicating that one agent node is not available toperform the scheduled backup in response to determining that the agentnode is not available to perform the scheduled backup, wherein the agentnode indicated as not available is not contacted during a subsequentprocessing of the scheduled backup.
 6. The method of claim 4, whereinthe agent nodes are contacted in a serial order, further comprising:contacting another agent node according to the serial order to determinewhether the agent node is capable of performing the scheduled backup inresponse to determining that a previously contacted agent node is notavailable to perform the backup.
 7. The method of claim 4, whereincontacting the at least one agent node further comprises: broadcasting amessage to all agent nodes to determine which agent nodes are availableto backup the scheduled backup data sets; and selecting at least oneagent node to perform the scheduled backup that responds to thebroadcast message indicating availability to perform the scheduledbackup.
 8. The method of claim 7, wherein selecting the at least oneagent mode comprises: selecting multiple agent nodes that respondindicating availability to perform the scheduled backup to perform thescheduled backup; and assigning a portion of the scheduled data sets toeach of the selected agent nodes to perform the scheduled backup withrespect to the assigned portion.
 9. The method of 1, wherein the agentnodes backup the scheduled data sets to a backup storage device.
 10. Themethod of claim 1, wherein the at least one agent node performing thescheduled backup acts on behalf of the backup node when performing thescheduled backup operations.
 11. The method of claim 10, furthercomprising: receiving a request to logon by one agent node performingthe scheduled backup using an agent node credential; and receiving arequest by the agent node logged on with the agent node credential tooperate as the backup node, wherein the agent node performs operationsto backup the scheduled data sets acting on behalf of the backup node;logging information on operations the agent node performs to backup thescheduled data sets as operations of the backup node.
 12. The method ofclaim 11, further comprising: indicating in the logging information thatthe agent node is operating as the backup node.
 13. A system incommunication with machines over a network, wherein a plurality of agentnodes are associated with machines in the network, comprising: aprocessor; and a computer readable medium include code capable ofcausing the processor to perform operations, the operations comprising:(i) associating backup data sets on at least one of the machines in thenetwork with a backup node; (ii) associating a plurality of agent nodesin the network with the backup node, wherein the agent nodes are capableof backing up the backup data sets associated with the backup node;(iii) processing a schedule indicating a scheduled backup to backupscheduled data sets associated with the backup node; and (iv) contactingat least one of the agent nodes to request the at least one agent nodeto perform the scheduled backup and backup the scheduled data sets,wherein the at least one contacted agent node performs the scheduledbackup to backup the scheduled backup sets.
 14. The system of claim 13,wherein the backup node comprises a virtual node, and wherein at leastone backup data set associated with the backup node is implementedwithin one node on the network that is different from at least one agentnode associated with the backup node.
 15. The system of claim 13,wherein the system is in communication with storage devices in thenetwork, wherein scheduled data sets are located on the storage devicesin the network, wherein the agent nodes backup the scheduled data setsby communicating with the storage devices over the network to cause atransfer of the scheduled data sets from the storage devices to backupstorage.
 16. The system of claim 13, wherein communicating with the atleast one agent node comprises: contacting at least one agent node todetermine whether the agent node is available to perform the scheduledbackup; and assigning the scheduled backup to the contacted agent nodein response to determining that the agent node is available to performthe scheduled backup.
 17. The system of claim 16, wherein the operationsfurther comprise: indicating that one agent node is not available toperform the scheduled backup in response to determining that the agentnode is not available to perform the scheduled backup, wherein the agentnode indicated as not available is not contacted during a subsequentprocessing of the scheduled backup.
 18. The system of claim 16, whereinthe agent nodes are contacted in a serial order, wherein the operationsfurther comprise: contacting another agent node according to the serialorder to determine whether the agent node is capable of performing thescheduled backup in response to determining that a previously contactedagent node is not available to perform the backup.
 19. The system ofclaim 16, wherein contacting the at least one agent node furthercomprises: broadcasting a message to all agent nodes to determine whichagent nodes are available to backup the scheduled backup data sets; andselecting at least one agent node to perform the scheduled backup thatresponds to the broadcast message indicating availability to perform thescheduled backup.
 20. The system of claim 19, wherein selecting the atleast one agent mode comprises: selecting multiple agent nodes thatrespond indicating availability to perform the scheduled backup toperform the scheduled backup; and assigning a portion of the scheduleddata sets to each of the selected agent nodes to perform the scheduledbackup with respect to the assigned portion.
 21. The system of claim 13,wherein the agent nodes backup the scheduled data sets to a backupstorage device.
 22. The system of claim 13, wherein the at least oneagent node performing the scheduled backup acts on behalf of the backupnode when performing the scheduled backup operations.
 23. The system ofclaim 22, wherein the operations further comprise: receiving a requestto logon by one agent node performing the scheduled backup using anagent node credential; receiving a request by the agent node logged onwith the agent node credential to operate as the backup node, whereinthe agent node performs operations to backup the scheduled data setsacting on behalf of the backup node; and logging information onoperations the agent node performs to backup the scheduled data sets asoperations of the backup node.
 24. The system of claim 23, wherein theoperations further comprise: indicating in the logging information thatthe agent node is operating as the backup node.
 25. An article ofmanufacture including code enabled to communicate with machines over anetwork, wherein a plurality of agent nodes are associated with machinesin the network, wherein the code is capable of causing operations to beperformed, the operations comprising: associating backup data sets on atleast one machine in a network with a backup node; associating aplurality of agent nodes in the network with the backup node, whereinthe agent nodes are associated with machines in the network capable ofbacking up the backup data sets associated with the backup node;processing a schedule indicating a scheduled backup to backup scheduleddata sets associated with the backup node; and contacting at least oneof the agent nodes to request the at least one agent node to perform thescheduled backup and backup the scheduled data sets, wherein the atleast one contacted agent node performs the scheduled backup to backupthe scheduled backup sets.
 26. The article of manufacture 25, whereinthe backup node comprises a virtual node, and wherein at least onebackup data set associated with the backup node is implemented withinone node on the network that is different from at least one agent nodeassociated with the backup node.
 27. The article of manufacture 25,wherein the scheduled data sets are located on storage devices in thenetwork, wherein the agent nodes backup the scheduled data sets bycommunicating with the storage devices over the network to cause atransfer of the scheduled data sets from the storage devices to backupstorage.
 28. The article of manufacture 25, wherein communicating withthe at least one agent node comprises: contacting at least one agentnode to determine whether the agent node is available to perform thescheduled backup; and assigning the scheduled backup to the contactedagent node in response to determining that the agent node is availableto perform the scheduled backup.
 29. The article of manufacture 28,wherein the operations further comprise: indicating that one agent nodeis not available to perform the scheduled backup in response todetermining that the agent node is not available to perform thescheduled backup, wherein the agent node indicated as not available isnot contacted during a subsequent processing of the scheduled backup.30. The article of manufacture 28, wherein the agent nodes are contactedin a serial order, wherein the operations further comprise: contactinganother agent node according to the serial order to determine whetherthe agent node is capable of performing the scheduled backup in responseto determining that a previously contacted agent node is not availableto perform the backup.
 31. The article of manufacture 28, whereincontacting the at least one agent node further comprises: broadcasting amessage to all agent nodes to determine which agent nodes are availableto backup the scheduled backup data sets; and selecting at least oneagent node to perform the scheduled backup that responds to thebroadcast message indicating availability to perform the scheduledbackup.
 32. The article of manufacture 31, wherein selecting the atleast one agent mode comprises: selecting multiple agent nodes thatrespond indicating availability to perform the scheduled backup toperform the scheduled backup; and assigning a portion of the scheduleddata sets to each of the selected agent nodes to perform the scheduledbackup with respect to the assigned portion.
 33. The article ofmanufacture 25, wherein the agent nodes backup the scheduled data setsto a backup storage device.
 34. The article of manufacture 25, whereinthe at least one agent node performing the scheduled backup acts onbehalf of the backup node when performing the scheduled backupoperations.
 35. The article of manufacture 34, wherein the operationsfurther comprise: receiving a request to logon by one agent nodeperforming the scheduled backup using an agent node credential;receiving a request by the agent node logged on with the agent nodecredential to operate as the backup node, wherein the agent nodeperforms operations to backup the scheduled data sets acting on behalfof the backup node; and logging information on operations the agent nodeperforms to backup the scheduled data sets as operations of the backupnode.
 36. The article of manufacture 25, wherein the operations furthercomprise: indicating in the logging information that the agent node isoperating as the backup node.